Patient hydration system with hydration state detection

ABSTRACT

A patient hydration system with a patient urine output measurement device, a hydration fluid administration subsystem, and a controller, responsive to the patient urine output measurement device. The controller is configured to control the hydration fluid administration subsystem to administer hydration fluid to the patient to prevent dehydration of the patient. A hydration sensor is also included to detect at least one patient parameter indicative of the patient&#39;s hydration state.

RELATED APPLICATIONS

This application is a continuation-in-part application of U.S. patent application Ser. No. 10/936,945, filed Sep. 9, 2004, entitled “Patient Hydration System and Method”.

FIELD OF THE INVENTION

This invention relates to a patient hydration system and method wherein the rate of hydration fluid delivered to the patient is automatically adjusted based on the urine output of the patient to maintain, as necessary, a zero, positive, or negative net fluid balance in the patient.

BACKGROUND OF THE INVENTION

The “cath lab” in a hospital is where a patient is injected with a radiocontrast media, imaged, diagnosed, and often operated on. Typically, a cardiologist refers the patient to the cath lab and the patient is instructed not to eat or drink the night before. In the case of a patient suffering a heart attack, the patient may be transferred directly to the cath lab.

Often, the patient is dehydrated when the patient arrives at the cath lab. The patient is prepped and the radiocontrast media injected. If, after imaging, a possible problem is detected, intervention occurs in the form of angioplasty, the placement of a stent, heart valve repair surgery, and the like. During these procedures, additional radiocontrast media may be injected into the patient and the patient imaged so the cardiac surgeon can view the progress of the operation.

Unfortunately, the radiocontrast media is toxic to the patient especially a patient who is dehydrated at the time the radiocontrast media is injected. A patient who already suffers from various medial problem such as diabetes or kidney problems is even more prone to medial problems due to the injection of the radiocontrast media.

It has been observed that dehydration increases the risk of radiocontrast nephropathy (RCN) when radiocontrast agents are injected into a patient during coronary and peripheral vascular catheterization procedures. RCN is the third most common cause of hospital-acquired renal failure. It occurs in over 5% of patients with any baseline renal insufficiency and in 50% of patients with preexisting chronic renal insufficiency and diabetes. Radiocontrast media has a variety of physiologic effects believed to contribute to the development of RCN. One of the main contributors is renal medullary ischemia, which results from a severe, radiocontrast-induced reduction in renal/intrarenal blood flow and oxygen delivery. The medullary ischemia induces ischemia and/or death of the metabolically active areas of the medulla responsible for urine formation, called the renal tubules. Medullary ischemia is attributed to the increase of oxygen demand by the kidney struggling to remove the radiocontrast media from blood plasma and excrete it from the body at the same time as the normal process of controlling the concentration of urine. Oxygen consumption in the medulla of the kidney is directly related to the work of concentrating urine. Since the presence of radiocontrast media in the urine makes it much more difficult for the kidney to concentrate urine, the work of the medulla outstrips the available oxygen supply and leads to medullary ischemia.

Although the exact mechanisms of RCN remain unknown, it has been consistently observed that patients with high urine output are less vulnerable to contrast injury. It is also clear that dehydration increases the risk of RCN, likely because urine (and contrast media inside the kidney) is excessively concentrated. As a result, patients predisposed to RCN are hydrated via intravenous infusion of normal saline before, during and after the angiographic procedure. Hydration is commonly performed at a conservative rate, especially in patients with existing heart and kidney dysfunction, since over-hydration can result in pulmonary edema (fluid in the lungs), shortness of breath, the need for intubation, and even death. Thus, the patients at highest risk for RCN are those least likely to receive the only proven therapy for preventing RCN (I.V. hydration) due to the unpredictability of side effects from I.V. hydration.

A major limitation to the more widespread use of the already known therapeutic, or optimal, levels of I.V. hydration is the current inability to balance the amount of fluid going into the patient to the amount of fluid being removed or excreted from the patient. It is possible to have a nurse measure a patient's urine output frequently but this method is impractical as nurses are often responsible for the care of many patients. In addition, the only accurate method of measuring urine output is to place a catheter into the patient's urinary bladder. Without a catheter, the patient must excrete the urine that may have been stored in the bladder for several hours. During this time, the amount of I.V. hydration can be significantly less than the amount of urine produced by the kidneys and stored in the bladder, leading to dehydration. Since patients do not normally have such a catheter during procedures using radiocontrast media, a valid measurement of urine output is not possible.

There seems to be indisputable scientific evidence that RCN in patients with even mild baseline renal insufficiency can lead to long term complications and even increased risk of mortality. This scientific knowledge has not yet been extended to daily clinical practice as routine monitoring of renal function post-catheterization is not performed and limits the identification of the known short-term clinical complications.

At the same time, there is a great deal of awareness in clinical practice that patients with serious renal insufficiency (serum creatinine (Cr)≧2.0) often suffer serious and immediate damage from contrast. Many cardiologists go considerable length to protect these patients including slow, overnight hydration (an extra admission day), administration of marginally effective but expensive drugs, or even not performing procedures at all.

There are approximately 1 million inpatient and 2 million outpatient angiography and angioplasty procedures performed in the U.S. per year (based on 2001 data). Based on the largest and most representative published studies of RCN available to us (such as Mayo Clinic PCI registry of 7,586 patients) we believe that 4% of patients have serious renal insufficiency (Cr≧2.0). This results in the initial market potential of 40 to 120 thousand cases per year from interventional cardiology alone. There is also a significant potential contribution from peripheral vascular procedures, CT scans and biventricular pacemaker leads placement. As the awareness of the RCN increases, the market can be expected to increase to 10% or more of all cases involving contrast.

According to the prior art, hydration therapy is given intravenously (I.V.) when someone is losing necessary fluids at a rate faster than they are retaining fluids. By giving the hydration therapy with an I.V., the patient receives the necessary fluids much faster than by drinking them. Also, dehydration can be heightened by hyperemesis (vomiting), therefore the I.V. method eliminates the need to take fluids orally. An anesthetized or sedated patient may not be able to drink. Hydration is used in clinical environments such as surgery, ICU, cathlab, oncology center and many others. At this time, hydration therapy is performed using inflatable pressure bags and/or I.V. pumps. A number of I.V. pumps on the market are designed for rapid infusion of fluids (as opposed to slow I.V. drug delivery) for perioperative hydration during surgery, ICU use and even emergency use for fluid resuscitation.

An infusion pump is a device used in a health care facility to pump fluids into a patient in a controlled manner. The device may use a piston pump, a roller pump, or a peristaltic pump and may be powered electrically or mechanically. The device may also operate using a constant force to propel the fluid through a narrow tube, which determines the flow rate. The device may include means to detect a fault condition, such as air in, or blockage of, the infusion line and to activate an alarm.

An example of a device for rapid infusion of fluids is the Infusion Dynamics (Plymouth Meeting, Pa.) Power Infuser. The Power Infuser uses two alternating syringes as a pumping engine. Since it is only intended to deliver fluids (not medication), the Power Infuser has accuracy of 15%. It provides a convenient way to deliver colloid as well as crystalloid for hydration during the perioperative period among other possible clinical settings. The Power Infuser provides anesthesiologists with the ability to infuse at rates similar to that seen with pressure bags, but with more exact volume control. The maximum infusion rate is 6 L/hr. It has the flexibility of infusing fluid at 0.2, 1, 2, 4 and 6 L/hr. A bolus setting of 250 mL will deliver that volume in 2.5 min. In a large blood loss surgical case, the use of Power Infuser enables large volumes of colloid to be delivered to restore hemodynamics.

It is also known in the art that loop diuretics such as furosemide (frusemide) reduce sodium reabsorption and consequentially reduce oxygen consumption of the kidney. They also reduce concentration of contrast agents in the urine-collecting cavities of the kidney. They induce diuresis (e.g., patient produces large quantities of very dilute urine) and help remove contrast out of the kidney faster. Theoretically, they should be the first line of defense against RCN. In fact, they were used to prevent RCN based on this assumption until clinical evidence suggested that they were actually deleterious. More recently, doubts have been raised regarding the validity of those negative clinical studies.

In two clinical studies by Solomon R., Werner C, Mann D. et al. “Effects of saline, mannitol, and furosemide to prevent acute decreases in renal function induced by radiocontrast agents”, N Engl J Med, 1994; 331:1416-1420 and by Weinstein J. M., Heyman S., Brezis M. “Potential deleterious effect of furosemide in radiocontrast nephropathy”, Nephron 1992; 62:413-415, as compared with hydration protocol, hydration supplemented with furosemide adversely affected kidney function in high-risk patients given contrast. Weinstein et al. found that furosemide-treated subjects lost 0.7 kg on average, whereas a 1.3-kg weight gain was noted in patients randomized to hydration alone, suggesting that in furosemide-treated subjects the hydration protocol has been insufficient and patients were dehydrated by excessive diuresis.

The clinical problem is simple to understand: diuresis is widely variable and unpredictable but the fluid replacement (hydration) at a constant infusion rate is prescribed in advance. To avoid the risk of pulmonary edema, fluid is typically given conservatively at 1 ml/hr per kg of body weight. The actual effect of diuretic is typically not known for 4 hours (until the sufficient amount of urine is collected and measured) and it is too late and too difficult to correct any imbalance. Meanwhile, patients could be losing fluid at 500 ml/hour while receiving the replacement at only 70 ml/hour. The effects of forced diuresis without balancing are illustrated in the research paper by Wakelkamp et. al. “The Influence of Drug input rate on the development of tolerance to furosemide” Br J. Clin. Pharmacol. 1998; 46: 479-487. In that study, diuresis and natriuresis curves were generated by infusing 10 mg of I.V. furosemide over 10 min to human volunteers. From that paper it can be seen that a patient can lose 1,300 ml of urine within 8 hours following the administration of this potent diuretic. Standard unbalanced I.V. hydration at 75 ml/h will only replace 600 ml in 8 hours. As a result the patient can lose “net” 700 ml of body fluid and become dehydrated. If such patient is vulnerable to renal insult, they can suffer kidney damage.

To illustrate the concept further, the effects of diuretic therapy on RCN were recently again investigated in the PRINCE study by Stevens et al. in “A Prospective Randomized Trial of Prevention Measures in Patients at High Risk for Contrast Nephropathy, Results of the PRINCE. Study” JACC Vol. 33, No. 2, 1999 February 1999:403-11. This study demonstrated that the induction of a forced diuresis while attempting to hold the intravascular volume in a constant state with replacement of urinary losses provided a modest protective benefit against contrast-induced renal injury, and importantly, independent of baseline renal function. This is particularly true if mean urine flow rates were above 150 ml/h. Forced diuresis was induced with intravenous crystalloid, furosemide, and mannitol beginning at the start of angiography.

The PRINCE study showed that, in contrast to the Weinstein study, forced diuresis could be beneficial to RCN patients if the intravascular volume was held in a constant state (no dehydration). Unfortunately, there are currently no practical ways of achieving this in a clinical setting since in response to the diuretic infusion the patient's urine output changes rapidly and unpredictably. In the absence of special equipment, it requires a nurse to calculate urine output every 15-30 minutes and re-adjust the I.V. infusion rate accordingly. While this can be achieved in experimental setting, this method is not possible in current clinical practice where nursing time is very limited and one nurse is often responsible for monitoring the care of up to ten patients. In addition, frequent adjustments and measurements of this kind often result in a human error.

Forced hydration and forced diuresis are known art that has been practiced for a long time using a variety of drugs and equipment. There is a clear clinical need for new methods and devices that will make this therapy accurate, simple to use and safe.

SUMMARY OF THE INVENTION

It is therefore an object of this invention to provide a patient hydration system and method.

It is a further object of this invention to provide such a system and method which prevents kidney damage in a patient.

It is a further object of this invention to provide such a system and method which protects the patient undergoing a medical procedure involving a radiocontrast agent from kidney damage.

It is a further object of this invention to provide such a system and method which incorporates a balancing feature intended to prevent dehydration, overhydration, and to maintain a proper intravascular volume.

It is a further object of this invention to provide a balanced diuresis method which automatically balances fluid loss in the urine.

It is a further object of this invention to provide such a system and method which is accurate, easy to implement, and simple to operate.

It is a further object of this invention to provide such a system and method which is particularly useful in the clinical setting of forced diuresis with drugs known as I.V. loop diuretics.

It is a further object of this invention to provide such a system and method in which the patient's hydration state is determined.

The subject invention results from the realization that radiocontrast nephropathy in particular and patient dehydration in general can be prevented by automatically measuring the urine output of the patient and adjusting the rate of delivery of a hydration fluid to the patient to achieve, as necessary, a zero, positive, or negative net fluid balance in the patient. Further, the patient's hydration state is determined and can be used to further adjust the rate of delivery of hydration fluid to the patient.

The subject invention, however, in other embodiments, need not achieve all these objectives and the claims hereof should not be limited to structures or methods capable of achieving these objectives.

In one aspect, this invention features a patient hydration system comprising a patient urine output measurement device, a hydration fluid administration subsystem, and a controller, responsive to the patient urine output measurement device, configured to control the hydration fluid administration subsystem to administer hydration fluid to the patient to prevent dehydration of the patient. Also included is a hydration sensor which detects at least one patient parameter indicative of the patient's hydration state.

Typically, the hydration sensor has an output connected to the controller and the controller determines the patient's hydration state based on the at least one patient parameter. The controller can be configured to output an indication of the patient's hydration state. Also, the controller can be configured to control the hydration fluid administration subsystem to administer hydration fluid to the patient based on the patient's urine output and also based on the patient's hydration state.

One example of a patient urine output measurement device includes a urine reservoir connected to the patient and a weighing mechanism for weighing the urine reservoir. The typical hydration fluid administration subsystem includes a pump responsive to a source of hydration fluid. The hydration sensor may be integral with the urine reservoir, responsive to the patient's urine, and the at least one patient parameter is a urine parameter such as urine conductivity, urine color, specific gravity, and the like.

One patient hydration balancing system in accordance with this invention features a patient urine output measurement device, a hydration sensor which detects at least one urine parameter indicative of the patient's hydration state, a hydration fluid administration subsystem, and a controller responsive to the patient urine output measurement device, configured to control the hydration fluid administration subsystem based on the patient's urine output, to determine the patient's hydration state based on the at least one urine parameter, and to control hydration fluid administration subsystem based on the patient's hydration state and/or to provide an output indicative of the patient's hydration state.

One particular fluid management system for a patient injected with a contrast agent in accordance with this invention features a console for mounting on an IV pole. A first attachment mechanism extends from the console for hanging a urine collection chamber. A first weighing device is associated with the console and is responsive to the first attachment. A second attachment extends from the console for hanging a source of hydration fluid and a second weighing device is associated with the console and responsive to the second attachment for weighing the source of hydration fluid. An infusion pump is integrated with the console and configured to pump hydration fluid from the source of hydration fluid to the patient. A hydration sensor detects at least one patient parameter indicative of the patient's hydration state. A controller in the console is responsive to the first and second weighing devices and the hydration sensor. The controller is configured to determine the patient's hydration state based on the at least one patient parameter and to control the infusion pump to hydrate the patient based on the patient's urine output and hydration state to prevent radiocontrast nephropathy.

One patient hydration method in accordance with this invention includes administering hydration fluid to a patient at an infusion rate, measuring the patient's urine output, and determining the patient's hydration state. The hydration fluid infusion rate is controlled based on the patient's urine output and the patient's hydration state.

Determining the patient's hydration state typically includes analyzing the patient's urine to detect a urine parameter indicative of the patient's hydration state such as urine conductivity, urine color, specific gravity, and the like. Typically, measuring the patient's urine output includes weighing the patient's urine output. Administering hydration fluid typically includes pumping hydration fluid into the patient. Controlling the hydration fluid infusion rate typically includes controlling an infusion pump.

BRIEF DESCRIPTION OF THE DRAWINGS

Other objects, features and advantages will occur to those skilled in the art from the following description of a preferred embodiment and the accompanying drawings, in which:

FIG. 1 is a schematic view of one example of a patient hydration system in accordance with the subject invention;

FIG. 2 is a flow chart depicting the primary steps associated with the programming of the controller shown in FIG. 1;

FIG. 3 is a schematic view of one embodiment of a patient hydration system in accordance with the subject invention wherein the weight of the urine output by a patient is measured and used as an input to control the infusion rate of an infusion pump;

FIG. 4 is a flow chart depicting one example of the software associated with a controller for adjusting the infusion rate based on the amount of urine output by the patient and the hydration state of the patient;

FIG. 5 is a schematic cross-sectional view showing one embodiment of a hydration sensor which detects the conductivity of the patient's urine in accordance with the subject invention;

FIG. 6 is a schematic cross-sectional view showing another embodiment of a hydration sensor which detects the color of the patient's urine;

FIG. 7 is a schematic cross-sectional view showing an embodiment of a hydration sensor which detects the specific gravity of the patient's urine in accordance with the subject invention;

FIG. 8 is a schematic block diagram depicting one example of how the controller of the subject invention provides redundancy in the measurement of the amount of hydration fluid administered to a patient by monitoring the operation of the hydration pump and also by monitoring the weight of the source of hydration fluid;

FIG. 9 is a block diagram showing the primary steps associated with the programming of the controller shown in FIG. 8;

FIGS. 10A-10D are graphs showing signals indicative of an abnormal urine output weight measurement;

FIGS. 11A-11B are graphs showing signals indicative of an abnormal hydration fluid bag weight measurement;

FIG. 12 is a flow chart showing the primary steps associated with the programming of the controller shown in FIG. 8;

FIGS. 13-14 are simplified graphs depicting how the hydration fluid administration rate is increased after a disruption in accordance with the subject invention;

FIG. 15 is a schematic front view of an example of a user interface in accordance with the subject invention;

FIG. 16 is a block diagram of an example of a main printed circuit board for an embodiment of a hydration system in accordance with this invention;

FIG. 17 is a timing diagram for the microprocessor and Complex Programmable Logic Device (CPLD) shown in FIG. 14;

FIG. 18 is a schematic front view of a prototype system in accordance with the subject invention; and

FIG. 19 is a schematic partial view of console user interface shown in FIG. 18.

DISCLOSURE OF THE PREFERRED EMBODIMENT

Aside from the preferred embodiment or embodiments disclosed below, this invention is capable of other embodiments and of being practiced or being carried out in various ways. Thus, it is to be understood that the invention is not limited in its application to the details of construction and the arrangements of components set forth in the following description or illustrated in the drawings. If only one embodiment is described herein, the claims hereof are not to be limited to that embodiment. Moreover, the claims hereof are not to be read restrictively unless there is clear and convincing evidence manifesting a certain exclusion, restriction, or disclaimer.

Patient hydration system 10, FIG. 1 according to this invention includes urine collection system 12 connected to patient P. Infusion system 20 typically includes an infusion device such as infusion pump 22 (e.g., a peristaltic pump) connected to source 24 of infusion fluid 26 (e.g., saline) by tubing 28. I.V. needle 30 is inserted in a vein of patient P and is connected to infusion pump 22 via tubing 32.

A control system or hydration balance means 34 detects the amount of urine output by the patient (by weighing the urine, measuring urine flow, and the like) and automatically adjusts the infusion rate of infusion pump 22 to achieve, as necessary, a zero, positive, or negative net fluid balance in the patient. Typically, urine collection system 12 includes catheter 14 (e.g., a Foley catheter) placed in the bladder B of patient P. Tubing 16 connects catheter 14 to meter 36. Controller 38, typically programmable, is responsive to the output of meter 36 and is configured to adjust the infusion rate of infusion pump 22.

Hydration sensor 11 detects at least one patient parameter indicative of the patient's hydration state. As noted in the background section above, a patient is often dehydrated when the patient arrives at the cath lab. Thus, detecting the patient's hydration state can be important even before hydration fluid is administered to the patient. Also, as controller 38 controls the operation of pump 22 to administer hydration fluid to the patient based on the patient's urine output, the patient's hydration state can be used as an input to controller 38 in order to provide a proper hydration balance and/or to provide an indication when hydration system 10 is working as expected.

Thus, in the preferred embodiment, hydration sensor 11 has an output connected to controller 38 as shown by line 13. Hydration sensor 11 outputs a signal on line 13 to controller 38 indicative of a patient parameter and, based on the parameter, controller 38 determines the patient's hydration state. Controller 38 may then provide an output 15 indicating, on a display for example, the patient's hydration state. In other embodiments, however, hydration sensor 11 could be equipped with a processor which outputs, on line 13, a signal indicating of the patient's hydration state after hydration sensor 11 determines the hydration state based on the patient parameter.

Typically, controller 38, FIG. 1 determines the patient's urine output via meter 36, step 110, FIG. 2 and also determines the patient's hydration state via hydration sensor 11, FIG. 1, step 111, FIG. 2. One or both of these determinations can be output to a monitor or console, if desired.

In one example, based on both of these determinations, i.e. urine output and the patient's hydration state, controller 38, FIG. 1 calculates the desired infusion rate, step 114, FIG. 2 and adjusts the hydration pump setting, step 166 to control pump 22, FIG. 1 accordingly.

In one illustrative example, a patient's hydration state is normal, his urine output is 1 liter/hour, and the controller controls the infusion pump to administer hydration fluid at 1 liter per hour. In another example, a patient's hydration state is well below normal (dehydrated), his urine output is 1 liter/hour, but the controller now controls the infusion pump to administer hydration fluid at 2 liters per hour until the patient's hydration state becomes normal and thereafter the controller controls the infusion pump to administer hydration fluid at 1 liter/hour.

In the embodiment of FIG. 3, console 82 is featured. The patient (See FIG. 1) is placed on the hospital bed or operating table 80. The hydration I.V. 30 and the urinary collection (Foley) catheter 14 are inserted using standard methods. The controller electronics and the infusion pump 22′ are integrated in the single enclosure of the control subsystem 34″ console 82. Console 82 is mounted on I.V. pole 84 for portability.

Control subsystem 34″ may also include electronic air detector 86 that prevents infusion of air into the patient. The air detector 86 is of ultrasonic type and can detect air in amounts exceeding approximately 50 micro liters traveling inside the infusion tubing 32. In one example, air detector 86 employs technology based on the difference of the speed of sound in liquid and in gaseous media. If an air bubble is detected, the pump 22′ is stopped almost instantaneously.

Console 82 may include one electronic strain gage or other weighing means to periodically detect the weight of the collected urine 51 in chamber 52 and, another electronic strain gauge to detect the weight of the remaining hydration fluid 26 in chamber 24. In the proposed embodiment, bag 52 with collected urine 51 and the bag 24 with hydration fluid 26 are hanging off the attachments (e.g., hooks) 90 and 92 connected to the strain gauges. Cable 91 interconnects hook 90 with urine collection bag 52 to keep urine collection bag 52 below the elevation of the patient. The bags with fluids are suspended from the hooks and a system of levers translate force to weight. The strain gauges convert force into an electronic signal that can be read by controller 34″. Suitable electronic devices for accurately measuring weight of a suspended bag with urine are available from Strain Measurement Devices, 130 Research Parkway, Meriden, Conn., 06450. These devices include electronics and mechanical components necessary to accurately measure and monitor weight of containers with medical fluids such as one or two-liter plastic bags of collected urine. For example, the overload proof single point load cell model S300 and the model S215 load cell from Strain Measurement Devices are particularly suited for scales, weighing bottles or bags in medical instrumentation applications. Options and various specifications and mounting configurations of these devices are available. These low profile single point sensors are intended for limited space applications requiring accurate measurement of full-scale forces of 2, 4, and 12 pounds-force. They can be used with a rigidly mounted platform or to measure tensile or compressive forces. A 10,000Ω wheatstone bridge offers low power consumption for extended battery life in portable products. Other examples of gravimetric scales used to balance medical fluids using a controller controlling the rates of fluid flow from the pumps in response to the weight information can be found in U.S. Pat. Nos. 5,910,252; 4,132,644; 4,204,957; 4,923,598; and 4,728,433 incorporated herein by this reference.

It is understood that there are many known ways in the art of engineering to measure weight and convert it into computer inputs. Regardless of the implementation, the purpose of the weight measurement is to detect the increasing weight of the collected urine 51 in the bag 52 and to adjust the rate of infusion or hydration based on the rate of urine flow.

Console 82 is also typically equipped with the user interface. The interface allows the user to set (dial in) the two main parameters of therapy: the duration of hydration and the desired net fluid balance at the end. The net fluid balance can be zero if no fluid gain or loss is desired. Display indicators on the console show the current status of therapy: the elapsed time 100 and the net fluid gain or loss 102.

The user interface may also include alarms 104. The alarms notify the user of therapy events such as an empty fluid bag or a full collection bag as detected by the weight scale. In one proposed embodiment, the urine is collected by gravity. If urine collection unexpectedly stops for any reason, the system will reduce and, if necessary, stop the IV infusion of fluid and alarm the user. Alternatively, the console can include the second (urine) pump similar to infusion pump 22. This configuration has an advantage of not depending on the bag height for drainage and the capability to automatically flush the catheter 14, FIG. 3 if it is occluded by temporarily reversing the pump flow direction.

In this embodiment, hydration sensor 11′ is typically responsive to the patient's urine 51 in reservoir 52 to determine the hydration state based on at least one parameter associated with the patient's urine, e.g., color, conductivity, specific gravity, and the like. Typically, hydration sensor 11′ is integral with reservoir 52. In but one example, sensor 11′ detects the conductivity of the patient's urine and outputs a signal on line 13′ to the controller within console 82 which is configured to determine the patient's hydration state and to output an indication thereof to be displayed on readout 101 and/or to control the operation of pump 22′ based on the patient's hydration state in addition to the patient's urine output weight. Hydration sensor 11″, in contrast, is located in urine line 16 as discussed below.

FIG. 4 illustrates an algorithm that can be used by the controller software of controller 34″ to execute the desired therapy. The algorithm is executed periodically based on a controller internal timer clock. It is appreciated that the algorithm can be made more complex to improve the performance and safety of the device. Controller 34″, FIG. 3 is programmed to determine the rate of change of the urine weight, steps 110 and 112, FIG. 4 and to determine the patient's hydration state, step 111′ in order to calculate a desired infusion rate, step 114, and to adjust the infusion rate of the infusion pump 22, FIG. 3 based on the calculated desired infusion rate, step 116, FIG. 4.

So far, the subject invention has been described in connection with the best mode now known to the applicant. The subject invention, however, is not to be limited to these disclosed embodiments. Rather, the invention covers all of various modifications and equivalent arrangements included within the spirit and scope of the appended claims. Particularly, the embodiments used to illustrate the invention use the weight of the collected urine for balancing. It is understood that it is the volume of the urine that is clinically important but the weight of the urine is equivalent for any practical purpose. For the purpose of this application, 100 grams of urine are the same as 100 ml of urine. It is believed at the time of the subject invention that measuring weight is more practical than measuring volume and that the weight is often used as a clinically acceptable substitute of volume of liquids that consist mostly of water. For practical purposes, the specific gravity (specific gravity of a substance is a comparison of its density to that of water) of urine and hydration fluids is the same as water. Those skilled in the art will realize that it is possible to measure volume directly using a meter which monitors the height of the column of the liquid in a vessel or by integrating the known volume of strokes of the pump over time. The exact meter used does not change the subject invention in regard to the balancing of urine output with hydration. A flow meter, for example, could be used to measure the urine output of patient P and a signal corresponding to the flow rate provided to controller 38, FIG. 1. A urine flow meter can be one of the devices disclosed in U.S. Pat. Nos. 5,891,051; 5,176,148; 4,504,263; and 4,343,316 hereby incorporated herein by this reference.

Also a medical device manufacturer, SFM Ltd., 14 Oholiav Street, Jerusalem, 94467, Israel manufactures and markets an electronic flow meter suitable for use with this invention. According to the manufacturer SFM Ltd. the UREXACT 2000 System is an accurate electronic urine-measuring device that combines an innovative disposable collection unit with a re-usable automatic electronic meter to provide precise urine monitoring. The UREXACT 2000 is based on the ultrasonic method of measuring fluid flow.

FIGS. 5-7 depict several options for specific in-line hydration sensors shown schematically for hydration sensor 11″, FIG. 3. Urine output line 16, FIG. 5 includes fitting 170 on line 16 and flow restrictor 172 to keep urine chamber 176 filled with urine. The output of flow restrictor 172 is connected to line 16′ which is connected to urine reservoir 52, FIG. 3. Spaced conductive plates 178 a and 178 b connected to a voltage source by wires 180 measure the conductivity of the patient's urine in chamber 176 in order to determine the patient's hydration state.

In another example, fitting 182 includes a source of illumination 184 such as a light emitting diode (LED) (or multiple illumination sources or LEDs) and a detector 186 or multiple detectors responsive to illumination source 184 in order to detect the color of the patient's urine flowing in line 16 and thereby determine the patients hydration state.

In the embodiment of FIG. 7, fitting 188 is in the form of specific gravity sensor used to determine the patient's hydration state. Chamber 190 is kept full by the effect of gravity and one or more specific gravity balls 192 a and 192 b are disposed in chamber 190. There is an illumination source such as an LED and a detector pair for each ball as shown for LEDs 194 a-b and detectors 196 a-b. Each ball is the same size but the weight of the balls differ by a predetermined amount. The ball weights and sizes can be tailored, for example, such as when the patient's urine specific gravity is at least 1.015, both balls float and block their respective LEDs so the detectors have no output. When only ball 192 b sinks, light from LED 194 b strikes detector 196 b and its output, connected to controller 38, FIG. 1 enables the controller to assign a specific gravity to the patient's urine in the range of between 1.010-1.015. When both balls 192 a and 192 b sink, detectors 196 a and 196 b both provide an output and the controller is programmed to assign a specific gravity value of between 1.000-1.010. Generally, a specific gravity of 1.015 is considered normal, a specific gravity of 1.020 indicates a state of dehydration, and a specific gravity value of 1.000 indicates a very hydrated patient.

Based on these determinations, controller 38, FIG. 1 can generate an alarm message, adjust the rate of infusion by controlling pump 22, and the like as desired. To render fitting 188, FIG. 7 a less expensive disposable product, LEDs 194 a-b and/or detectors 196 a-b could be separate from fitting 188 (and within console 82, FIG. 3, for example) and fiber optic cables used to connect the LEDs and detectors to fitting 188.

Abnormal Condition Sensing and System Reliability

One potential concern with the use of the embodiment shown in FIG. 3 is that the weight of hydration fluid at any give time may not always provide a reliable indication of the true amount of hydration fluid injected into the patient via pump 22′. For example, IV Pole 84 and/or hydration fluid bag 24 could be jostled affecting the strain gauge measurement, hydration fluid bag 24 could leak or, when only partially emptied, replaced with a full bag, or bag 24 may not be hanging freely from hook 92.

Similarly, the operation of pump 22′ may not always provide a reliable indication of how much hydration fluid is actually injected into the patient due to inaccuracies in the pump electronics and the like.

In the subject invention, controller 38 (a microprocessor or microcontroller) in console 82, as shown in FIG. 8, controls hydration pump 22 to infuse the patient with hydration fluid based on the patient's urine output and keeps track of the hydration fluid injected in two ways to provide safety and redundancy. The preferred hydration fluid measurement subsystem includes, first, as discussed above, the weight of hydration fluid source 24, FIG. 3 which is monitored as shown at 200 in FIG. 8. Urine output is also monitored as shown at 201. In addition, the operation history of infusion pump 22 is monitored by controller 38. Controller 38 may store values representing both of these measurements in a memory such as PROM 202 and controller 38 is programmed as shown in FIG. 9 to store the hydration fluid amounts administered via the hydration fluid measurement strain gauge, step 220, FIG. 9, and controller 38 is also programmed to store the hydration fluid amount administered by monitoring of the hydration pump operation history, step 222. If there is a difference between these two stored values by a predetermined amount, step 224, an alarm signal (203, FIG. 8) can be generated, step 226 so that the potential problem can be corrected. Controller 38 can also be programmed to generate and output an alarm signal if, for example, the weight of saline bag indicates 50 cc of saline has been injected in the last 10 minutes but the pump operation history indicates only 20 cc of saline has been injected in the last 10 minutes. This condition would likely indicate the saline bag is not hanging free on hook 90, FIG. 3. The alarm signal can trigger a nurse to check the condition of the saline bag.

In another possible scenario, the pump operation history does not equate to an amount of hydration fluid administered commensurate with the weight of the saline bag. In such a scenario, controller 38 can be programmed to reset the pump and then adjust the operation of the pump to inject hydration fluid based on the patient's urine output and the weight of the saline bag.

Typically, the controller is also configured to operate pump 22 at predetermined maximum and minimum infusion rates irrespective of the weight of the saline bag (determined via a first strain gauge), the weight of the urine bag (determined by a second strain gauge), or the pump operation history. An acceptable maximum infusion rate may be 60 liters per minute in any 15 minute time period or 22 liters per hour at any time. An acceptable minimum infusion rate may be 1 milliliter per hour per kilogram of body weight to keep the patient's vein open at the site of the infusion IV needle 30, FIG. 3 irrespective of the weight of the urine bag.

It is preferable that in any embodiment the hydration system be portable since patients are often moved in and out and about the cath lab. When the embodiment of FIG. 3 is employed, for example, there are conditions and events wherein the weight of urine bag 52 may not be indicative of the true amount of urine output by the patient at any given time. FIG. 10A shows a signal received by the controller from a strain gauge which measures the weight of urine bag 52, FIG. 3 in a situation where the urine bag has been jostled. The signal portion 250, FIG. 10A is indicative of an abnormal patient urine output measurement.

FIG. 10B shows another abnormal patient urine output measurement signal indicative of a urine bag 52, FIG. 3 which has been emptied at time t₁. FIG. 10C shows another abnormal patient urine output measurement signal indicative of a potential problem since the patient's urine output is not increasing over time as expected. FIG. 10D shows another abnormal patient urine output measurement indicative of a potential problem since the patient's urine output is increasing, beginning at time t₂, at a rate higher than expected.

Similarly, it is possible that the weight of hydration fluid bag 24, FIG. 3 may not always be indicative of the true amount of hydration fluid administered to the patient in any given time period.

FIG. 11A is representative of the signal received by the controller from a strain gauge which measures the weight of hydration fluid bag 24, FIG. 3 in the case where the hydration fluid bag has been jostled.

Another abnormal hydration fluid measurement is shown in FIG. 11B which indicates that at time t₃ an empty hydration fluid bag has been replaced with a full hydration fluid bag.

In accordance with the preferred embodiment of the subject invention, controller 38, FIG. 8 is responsive, via the strain gauges or other measurement devices, to the urine bag weight and also the weight of the hydration fluid bag to achieve a predetermined hydration balance as discussed above, step 260, FIG. 12. Controller 38, FIG. 8 is also programmed to detect a) abnormal patient urine output measurements like those of FIGS. 10A-10D, step 222, FIG. 12 and b) abnormal hydration fluid measurements like those of FIGS. 11A-11B, step 264, FIG. 12. The controller is further programmed to take corrective action, steps 266 and 268 in response to these abnormal measurements. The corrective action typically depends on the specific abnormal indication. In the case of FIG. 10A, which likely is indicative of a jostled urine collection bag, the urine output measurement is sharply varying and the controller can be programmed to control the infusion pump to hydrate the patient at a preset minimum infusion rate, for example, 1 milliliter per hour per kilogram of patient body weight. This safe minimum level is often referred to as KVO for “keep vein open” in clinical practice. After the signal settles down as shown at time t₀ in FIG. 10A, the controller is programmed to hydrate the patient at an increased rate thereafter to achieve the predetermined hydration balance. The controller software calculates the amount of urine made by the patient during the occurrence of the sharply varying urine output signal and increases the infusion rate by controlling the infusion pump to give back to the patient the volume lost by the patient, the “owed volume”. The automatic administration of the “owed volume” exemplifies the corrective action. After the predetermined hydration balance is restored, the infusion rate is returned to the normal level so that the hydration fluid input level matches the urine output level plus or minus any desired net gain or loss. Urine output fluctuates in time and balancing is, in reality, dynamic based on small time increments. They can be less than 1 second long. At the end of each control interval, a new correction can be introduced by controller 38 to the infusion pump speed to achieve the goal of balancing in a smooth reasonable way at an allowed rate of change. It is not practical to administer all the “owed” volume immediately. The controller software gives back fluid in small safe increments over time, for example, a safe limit of no more than 250 milliliters over 15 minutes or a flow rate of no more than 6 liters per hour. Methods of such dynamic control are implemented in the controller software and the safe limits of infusion imbedded in the software or set by the user via the user interface of console 82, FIG. 3.

In another example, when controller 38, FIG. 8 detects the abnormal signal of FIG. 10A, the controller can be programmed to ignore errant signal portion 250 and control infusion pump 22, FIG. 8 to maintain infusion at the rate prior to errant signal portion 250, FIG. 10A. After the errant signal is no longer detected, infusion continues in accordance with FIG. 4. Rejection of the errant signal is another example of the corrective action by the system.

FIG. 10B illustrates a signal received by the controller indicative of a urine bag that has been at least partially emptied. Other possibilities include a urine collection bag which leaks or a drain valve that has not been completely closed. In such as situation, the controller software can be configured to control the operation of the infusion device based on the patient's urine output before and after the urine bag was emptied to achieve the predetermined hydration balance. That is, the controller software extrapolates the urine bag weight as shown at 251 in FIG. 10B to provide a proper indication of the patient's urine output.

In FIG. 10C, the urine bag weight is not increasing as expected and the controller software recognizes and detects this abnormal patient urine output measurement and generates an alarm signal to be displayed on console 82, at display area 86, FIG. 3. Similarly, in FIG. 10D the urine bag weight sharply increases at time t₂ and the controller software is configured to generate another alarm signal.

In the case of abnormal hydration fluid measurement, FIG. 11A is indicative of a source of hydration fluid which has been jostled and the controller software is configured to take corrective action in a form of an alarm signal, for example.

FIGS. 13-14 illustrate the concept of “catching up” or “giving back” the hydration fluid “owed to the patient” when balancing is for some reason temporarily disrupted. Ideally, as the patient makes urine continuously at level 300 hydration would be balanced continuously. In reality, the process is frequently interrupted when the urine bag is full and drained, bags with hydration fluid are empty and replaced or when the patient is transported and accurate measurements of weight become impossible. In the cathlab environment patients are frequently moved from one location to another. It is an object of this invention to enable balanced hydration of the patient throughout the normal flow of the cathlab procedure.

As described above, balancing is implemented via periodic reading of weight scales. In the proposed example, bag 52, FIG. 3 with collected urine 53 and the bag 24 with hydration fluid 26 are hanging off the hooks 90 and 92 connected to the weight scales. The bags with fluids are suspended from the hooks that translate force to scales such as load cells with strain gages. Strain gage converts force into an electronic signal that can be read by the controller. Suitable electronic devices for accurately measuring weight of a suspended bag with urine are available from Strain Measurement Devices Inc., (Meriden, Conn.). In the preferred embodiment two strain gages model SMD S300 designated by this manufacturer as Load Cells with Integral Overload Protection and 2 Kg capacity are used to measure and balance weight (and volume) of fluid. These devices include electronics and mechanical components necessary to accurately measure and monitor weight of containers with medical fluids such as one or two-liter plastic bags of collected urine and hydration fluid. When the patient and the device are moved weight scales are effected by motion artifacts (inertia) and electronic signals often become unreliable.

The patient's hydration rate, FIG. 14 is set to the sum of balancing volume equal to urine output 300, FIG. 13 and net gain 304 during normal operation. During the time period t₁, a disruption is detected. For example, the urine bag may be drained or the weight scale readings are unreliable because of motion.

In one embodiment, the controller software responds in the following way.

The disruption is detected and the infusion rate is set to safe minimum level 310 often referred to as KVO for “keep vein open” in clinical practice. For example, KVO can be set to 1 ml/hour per kg of body weight or just 70 ml/h. When the end of the disruption is detected, the software calculates the amount of urine made by the patient during the disruption time using weight measurement. The system increases the infusion rate as shown at 312 to give back the volume lost by the patient—“owed volume”. After the balance is restored, the infusion rate is returned to normal level such as the balance plus the desired net gain 304.

The process so illustrated by FIG. 12 is greatly simplified to emphasize the point of restoring balance after disruption. It is understood that urine output fluctuates in time and balancing is in reality dynamic based on small time increments that can be less than one second long. At the end of each control interval new correction is introduced to the infusion pump speed to achieve the goal of balancing in a smooth reasonable way at an allowed rate of change. Even if the pump capacity allows it, it is not practical to infuse all the “owed” volume immediately. The software controls the infusion device to give back fluid in small safe increments spaced over time. For example safe limit can be set to no more of 250 ml over 15 minutes or flow rate of no more than 6 liters per hour. Methods of such dynamic control of volume are known in the field of control engineering and embedded real time software. Safe limits of therapy can be embedded in the software by the manufacturer or set by the user via user interface.

If the disruption is caused by the user changing an infusion fluid bag, infusion flow during the disruption is set to zero. The user can force this condition by using the ON/OFF button on the console. The pump should be stopped while user is spiking a new bag, otherwise air will be pumped. If a disruption is caused by user draining the urine bag, the infusion flow can be set to KVO level. The user can force this condition by pushing the PAUSE button on the console. Alternatively this condition can be automatically detected by the weight scale sensing abrupt reduction of urine bag weight. If the urine bag is full (as detected by maximum weight), the system automatically stops balancing and switches to the KVO mode. An alarm is issued to remind user to drain the bag some time before the bag is full. For example, if the bag volume is 2 liters, alarm can be issued when the urine weight corresponds to 1.8 liters of urine.

During pause mode, the controller software generates a low volume beeping alarm. After 15 minutes, the software increases the volume to high to attract attention of the user. At the same time visual indication such as a “PAUSE” message or a Pause LED is used to inform the user of the reason for device beeping.

Upon exit from Pause mode and into run mode, the software can automatically adapt to the infusion and urine bag weight changes to correctly resume hydration control. There are several ways to detect disruption caused by motion. In a simpler embodiment system software detects that the system console is unplugged from the AC wall outlet and operating on batteries. During battery operation balancing is turned off and KVO rate of infusion is set. When AC cord is plugged back in the disruption is considered to be over and the collected urine is measured and balanced as quickly as practical and safe. Alternatively the device can be equipped with a transport key commend activated by user. In a somewhat more complex embodiment software can analyze and detect fluctuations of weight caused by motion inertia and suspend balancing until reliable measurements are re-established.

A User Interface

FIG. 15 illustrates an example of a user interface of the proposed embodiment. In the proposed embodiment, the user interface consists of two Liquid Crystal Displays 320 and 322 and 11 function keys or buttons 328 a-328 j. The LCDs can be 2×24 LCD with LED backlight and 3.2×5.55 mm characters part number NHD-0224B0-FSW-GBW from New Haven Display International (Hoffman Estates, Ill.).

The function keys have following functions. Scroll Key 328 i is intended to be used to scroll through the system parameters displayed on 320. Parameters such as total urine made, time of therapy, net balance can be displayed at any time by user command.

Menu Key 328 b is intended to be used to view the system setting's menu. When in the menu mode user can change parameters of therapy such as desired hourly net gain, bolus amount or maximum amount of hydration allowed. Accept Key 328 a is intended to be used to enter (accept) inputs. Clear Key 328 c is intended to be used to cancel inputs and clear alarms. Up Arrow Key 328 h is intended to be used to increment settings and navigate the menus and Down Arrow Key 328 g is intended to be used to decrement settings and navigate the menus. Advance key 328 d is intended to allow manual operation. While key is pressed system rotates the pump at a preset speed. This mode is used to manually prime the circuit with fluid or advance air bubbles through the tubing.

For example, while the advance key is pressed, the software may run the pump at 60 ml/min. Advance mode may be stopped by releasing the advance key or when a timeout of 30 seconds of continuous operation has elapsed. After a time out, advance mode may be allowed after the advance key is released for 2 seconds.

Set Bolus Key 328 e is intended to allow setting of the bolus amount and duration. Pause Key 328 f is intended to pause the running system or resume operation if paused. After key 328 f is pressed, the system switches to fixed KVO infusion rate, no balancing is performed. This key can be used to suspend balancing while urine bag is drained. It can also be used when patient is moved and signals from weight scales are disturbed. When the system is paused it emits a beeping sound to alert the user. The status LCD displays a message indicating the pause state and the elapsed time in the pause state. Run/Stop Key 328 f is intended to run the system if stopped and stop the system if running.

Prime Key 328 j is intended to initiate a priming process and Silence Key 328 e is intended to silence the alarm audio. The prime Key initiates priming of the circuit with fluid to purge air. The software may enter prime mode to execute the prime test before entering run mode, if a new patient is selected or if the user has pressed the prime key. The prime mode may be cancelled by pressing the stop key.

In order to perform the prime test, the user connects the infusion output (tubing 32 on FIG. 3) to the urine input (tubing 16 on FIG. 3). Fluid path is set to pump from hydration bag 26 into urine bag 53. The software may operate the pump at a speed of 60 ml/min for a period of at least 2 minutes. This time is sufficient to fill the IV set with fluid and check the weight scale inputs. (The measured hydration fluid volume is expected to reduce while the measured urine output volume is expected to increase by the corresponding amount. Thus the pump and weight scales are tested). If the difference between the change in expected weights and actual weights is more than, for example, 20%, the software may generate an alarm. After priming, the controller software may display a message to the user that priming is completed and the system is ready for use. The prime test may complete execution within 5 minutes. The controller software may perform an air detector (86 on FIG. 3, which is in the fluid path) test and generate an alarm if it fails. The air detector is tested using the test signal which forces a liquid to air transition. The software may also test the operation of the pressure sensor during priming and generate an alarm on failure.

An Exemplary Circuit Architecture

In one particular example, the main circuit board for controller unit 82, FIG. 3 is shown in FIG. 16. Microprocessor 400 is an Atmel AT91SAM7S256 with an ARM7 core, 64 Kbytes internal RAM 402 and 256 Kbytes internal Flash 404. Infusion pump motor controller 406 is an off the shelf brushless DC motor controller which gets power from power management board 430 and uses internal RS232 interface to communicate with main microprocessor 400.

The load cell outputs for urine bag 52, FIG. 3 and saline bag 24 (load cells 408 and 410, FIG. 16) are amplified in differential circuit 412 and a signal is applied to differential analog to digital converter 414. Programmable logic device (CPLD) 416 is a Xilinx XC95144XL-10 TQ100. Pressure sensor 418 is a medical grade silicon pressure sensor. The sensor is supplied with 0.910 mA current from a high impedance current source to produce 2.3 V at 20 psi on the output of the instrumentation amplifier. Due to the circuit topology there is a constant offset of about 0.910V at the IA output at zero pressure. This offset is eliminated in the software. Air bubble detector 420 with its amplifier board is an off the shelf unit.

Each load cell 408, 410 can be compensated up to +/−1.49 kg by using DAC MAX525 422. This compensation is used to cancel out an offset caused by the load cell offset and gain errors.

At first power up, DAC MAX525 422 is set to middle scale for all the outputs. This step assures no effect on the offset in the load cell circuit. Saline and urine channels are compensated by pairs of DACs arranged in push-pull circuit giving the ability of positive and negative offset compensation. The preferred compensation can be achieved by iterative method. Using linear equation method may be sufficient to keep ADC 414 full scale in linear range.

Power Management board 430 contains all the circuit controlling operations of charging Lithium-Polymer battery 432 and switching between AC and battery power. The main power supply is a medical grade high-efficiency switching power supply. The Displays 401 and 403 and 8-Ohm speaker 432 are controlled by the main microprocessor 400. Piezo buzzer 452 is implemented to signal fault conditions which require operator attendance. Microprocessor 400 has a UART serial port connector 434 and an RS232 transceiver buffer 436 connects this port to a PC.

Microprocessor 400 interfaces with the external pins via its 32 PIO pins. These pins may have different functions as configured by software. Table 1 shows the functions wired to the PIO pins in the hardware. The shaded boxes in the table show the selections for each pin as “Peripheral A,” “Peripheral B” or assigned as an “I/O” pin. Note that the direction of the I/O pins may be input, output or bi-directional depending on pin function.

TABLE 1 Microprocessor PIO Pin Assignments I/O I/O Line Net Function Periph A Periph B Other Pin PIN # PA0 PB_EN_LCD1 Parallel Bus Enable for LCD #1 PWM0 TIOA0 Hi D I/O 48 PA1 MLED1 LED1 => Warning; Red LED on front panel PWM1 TIOB0 Hi D I/O 47 PA2 MLED2 LED2 => Power; Green LED on front panel PWM2 SCK0 Hi D I/O 44 PA3 TWD Two Wire Data TWD NPCS3 Hi D 43 PA4 TWCK Two Wire Clock TWCK TCLK0 36 PA5 RXD0 RS-232 RX 0 (motor control) RXDO NPCS3 35 PA6 TXD0 RS-232 TX 0 (motor control) TXD0 PCK0 34 PA7 mp_io1 Reset to CPLD and ADC RTS0 PWM3 I/O 32 PA8 PB_EN_LCD2 Parallel Bus Enable for LCD #2 CTS0 ADTRG I/O 31 PA9 RXD1 RS-232 RX for PC I/F DRXD NPCS1 I/O 30 PA10 TXD1 RS-232 TX for PC I/F DTXD NPCS2 I/O 29 PA11 ADC_CS# SPI chip select to ADC NPSC0 PWM0 28 PA12 MISO SPI data to uP MISO PWM1 27 PA13 MOSI SPI data from uP MOSI PWM2 22 PA14 SPCK SPI clock SPCK PWM3 21 PA15 I2S_WS Audio I/F word select TF TIOA1 I/O 20 PA16 I2S_SCK Audio I/F serial clock TK TIOB1 I/O 19 PA17 I2S_SD Audio I/F serial data TD PCK2 AD0 9 PA18 CLK_AUD_DAC Clock for the Audio DAC RD PCK2 AD1 I/O 10 PA19 FIQ Power Failure interrupt => Power loss in 50 ms. RK FIQ AD2 I/O 13 PA20 IRQ0_IO Air detector sense line RF IRQ0 AD3 I/O 16 PA21 MTRSHTDWN# Motor Shutdown (Low = shutdown) RXD1 PCK1 I/O 11 PA22 PROM_CS# SPI chip select to EEPROM TXD1 NPCS3 14 PA23 PB_D0 Parallel Bus Data bit 0 SCK1 PWM0 I/O 15 PA24 PB_D1 Parallel Bus Data bit 1 RTS1 PWM1 I/O 23 PA25 PB_D2 Parallel Bus Data bit 2 CTS1 PWM2 I/O 25 PA26 PB_D3 Parallel Bus Data bit 3 DCD1 TIOA2 I/O 26 PA27 PB_EN_CPLD Parallel Bus Enable for CPLD DTR1 TIOB2 I/O 37 PA28 PB_RW Parallel Bus Read/Not Write DSR1 TCLK1 I/O 38 PA29 PB_RS_AS Parallel Bus RS or AS RI1 TCLK2 I/O 41 PA30 ADC_DRDY#(IRQ1) ADC Data Ready (active low) IRQ1 NPCS2 I/O 42 PA31 DAC_CS# SPI chip select to DAC (Note: MP_IO2 line to CPLD) NPCS1 PCK2 I/O 52

ADC 44 is used to read the two load cells 408 and 410. Table 2 lists the purpose of the external ADC device inputs.

TABLE 2 External ADC Input Assignments Channel Number Input Purpose 0 Load Cell 0 Saline Bag Weight 1 Load Cell 1 Urine Bag Weight

ADC 414 is accessed from microprocessor 400 via the SPI port 440 using the chip select signal “ADC_CS#.” This chip select and the SPI interface are connected via the microprocessor's PIO interface (see Table 1).

The ADC ready is connected to the microprocessor physically through CPLD 416 but is unchanged by the CPLD and is provided to the microprocessor IRQ1 line as shown in the PIO pin list, Table 1.

Table 3 lists the register settings required for ADC operation.

TABLE 3 External ADC Device Register Settings Configuration Filter Function Register (Hex) Register (Hex) Standard Channel 1 C6 33 2-Channel Channel 2 56 33 Operation Operational Channel 1 4000C6 33 Test Channel 2 800056 33

ADC 450 inside microprocessor 400 is used to input data from pressure sensor 418, which is wired to the microprocessor's ADC4 input through conditioning amplifier 452. This input line is direct to the internal ADC and does not go through the PIO interface. Also, to verify the analog voltage (AVCC) in working is checked by measuring half the value on the ADC input. An SPI quad 12-bit DAC 422 is used set offset compensation on each channel.

Sound is generated by the Main board 401 in two ways. One way is strictly for an alarm function from CPLD watchdog circuitry 416 and controls piezo sound device 452. The second way is more versatile and is controlled by microprocessor 400 and uses audio DAC 454 device to speaker 432. This speaker output maybe used for general purpose sounds as well as a full feature alarm and alert sounds.

The I2S audio data output port from the microprocessor is connected to audio DAC 454 to control and generate the sound. Additionally, DAC volume is controlled via a Two-Wire Interface (TWI) also from the microprocessor to the audio DAC. Audio DAC 454 may be a Maxim MAX9850 with its output to a Texas Instruments TPA6211A1 mono audio amplifier to drive a speaker.

The audio DAC requires a clock in the range between 8.448 and 40 MHz and this clock is connected to the DAC from the microprocessor on the PCK2 line from the Programmable Clock Output Controller of the PMC module. A sampling frequency of 8 kHz should be used for the audio DAC to minimize the size of the data required.

Microprocessor settings for Audio DAC 454 are list in Table 4.

TABLE 4 Programming table for headphone amplifier MAX9850. Register Address Function B7 B6 B5 B4 B3 B2 B1 B0 0x2 Volume Mute 0 Slew 1 VOL(5:0) 0x00 0x3 General GM(1:0) GPD DBDEL(1:0) Mono 0 0 ZDEN Purpose 0x2 GPIO Debounce Delay Zero Output 1 0x01 Crossing 1 0x4 Interrupt 0 ISGPIO ICLK ISHPS IVMN 0 0 IICH Enable Allow PLL Headphone Minimum Overload 1 alerts 1 Lock 1 Detect 1 Volume 0 0x5 Enable SHDN* MCLKEN CPEN(1:0) HPEN LNOEN LNIEN DACEN Power On 1 DAC En 1 Charge Pump Headphone Line On 1 Line In 0 DAC En 1 0x3 output 1 0x6 Clock 0 0 0 0 IC(1:0) 0 0 Internal Clock Divide 0x0 0x7 Charge SR 0 CP(4:0) Pump Slew Rate (1:0) Charge pump divider 0x2 0x09 0x8 LRCLK INT MSB (14:8) MSB Integer/Float 0 RLCLK divider 0x0 0x9 LRCLK LSB (7:0) LSB RLCLK divider 0x0 0xA Digital MAS INV BCINV LSF DLY RTJ WS(1:0) Audio Master Channel Falling LSB first Second Right Word Size Order Edge Rising Justified 0x0 (16 bits) Latch Edge 0 0 0 0 1 0

Two LCD displays 320 and 324 are interfaced from microprocessor 400 via the “Parallel Bus” or PB_pins shown in the PIO table. The two enable signals PB_EN_LCD1 and PB_EN_LCD2 select the respective LCD. The signal PB_RS_AS is used for the LCD interface as the register select (RS) control.

Power Management board 430 consists of three major functions: (1) Battery Charger and Monitor 460, (2) Multiple Source Power Controller 462 and (3) Motor power shutoff 464. Multiple Source Power Controller 462 switches between the DC voltage from the power supply (18V nominal) and the battery source. The Two-wire interface connects to battery 432.

CPLD 416 has the watchdog alarm logic and the panel switch inputs. This interface uses the “Parallel Bus” (or PB_) which is shared with the LCD interface. Other hardware signals pass through the CPLD to provide a path to the microprocessor such as the ready signal from the ADC 414.

FIG. 17 shows the timing to read and write data from microprocessor 440 to CPLD 416. Registers in the CPLD are assumed to be 8 bits (or two nybbles), so there are two reads or two writes for each data cycle. The signal PB_RS_AS is used for the CPLD interface as the address select. The data bus, PB_D[3:0], has the register address when AS is high and the read or write data when AS is low. The address cycle is always a write from the microprocessor to the CPLD. The data cycle direction is determined by the PB_RW signal with active high as a read cycle.

The 16 CPLD 416 registers are 8 bits, though not all the registers are used. Table 5 lists the registers in the CPLD and the tables 6-12 describe the register bits.

TABLE 5 CPLD Registers List Read Register or Address Mnemonic Purpose Write (hex) CpldId CPLD Identification code == 0x51 R 0 CpldRev CPLD Revision code R 1 Diagnostic Diagnostic Register RW 2 WatchdogPet Watchdog pet register RW 3 Status Status Register R 4 Control Control Register W 5 SwitchesL Panel Switches 7:0 R 6 SwitchesH Panel Switches 15:8 R 7 MotorSpeedL Motor Speed bits 7:0 R 8 MotorSpeedH Motor Speed bits 15:8 R 9 Note: MotorSpeed is a 16 bit signed number for motor speed in units of RPM. A B ... F

TABLE 6 CpldId and CpldRev Register Format 7:0 ID[7:0] or Rev[7:0]

ID is the identification code of the DSP board, CPLD=TBD fixed. Rev is the revision code for the DSP board CPLD.

TABLE 7 Diagnostic Register 7 6 5 4 3 2 1 0 0 0 0 0 Hdr3 Hdr2 Hdr1 hdr0

Hdr[3:0] is the input from the four head lines on the board. Output (writes) to register are ignored.

TABLE 8 Status Register Bit Mnemonic Description 7 POWER_FAILURE# Power Failure. Also, goes to the FIQ (PA19) line of uP. When first goes low the uP power has 50 ms complete all tasks before losing power. 6 LOW_BATTERY LOBAT signal from the LT1479 5 DC_IN_GOOD DC Power from the power supply is good. When this flag is low the DC power is off and therefore the uP must be powered from the battery. 4 0 3 MtrPwrFdbk Motor Power Feedback. Indicates motor power state on the PM board. (Used with watchdog test.) 2 PumpDoorOpen Pump door is open flag 1 wdOut Watchdog output 0 AirDetectorIn Air Detector Input line (1 = air or air-bubbles; 0 = liquid only)

TABLE 9 Control Register Bit Mnemonic Description 7 Enable_piezo Enable piezo alarm device to sound when watchdog times out. 6 5 BATTERY_OFF Disconnect the battery under SW control. Used when the power supply off (DCIN off). uP power goes off after setting this control bit. 4 DCIN_BAT# Select power from the DC power supply when high, from the battery when low. This may be done automatically by the hardware if user disconnects AC power (DC_IN_GOOD=0). 3 CLED2 CPLD diagnostic LED #2 2 CLED1 CPLD diagnostic LED #1 1 0 AirDetectorTest Air Detector test output. Runs test when in set high when liquid is present. Software should turn bit off after setting. Signal is active low (test runs when low).

TABLE 10 Watchdog Register 3 2 1 0 3 2 1 0 0 1 1 1 0 1 0 1

wdec[3:0] is Write a 0x75 to “pet” the watchdog. No other value is valid.

TABLE 11 SwitchesL, Panel Switches 7:0 Bit Mnemonic Function 7 SW8 CLEAR 6 SW7 PRIME 5 SW6 SCROLL 4 SW5 (Upper Center) 3 SW4 ACCEPT 2 SW3 MENU 1 SW2 ADVANCE 0 SW1 BOLUS

TABLE 12 SwitchesH, Panel Switches 15:8 Bit Mnemonic Function 7 SW16 Not used = low 6 SW15 Not used = low 5 SW14 SILENCE 4 SW13 RUN/STOP 3 SW12 DOWN ARROW 2 SW11 PAUSE 1 SW10 UP ARROW 0 SW9 (Upper Right)

Exemplary Microprocessor Programming

One example of suitable programming for processor of controller 400 is set forth below.

////////////////////////////////////////////////////////////////////////////////////////// // Name : filterInfusionWeight // // Description : filter infusion weight using a moving average filter // and check for stable infusion // scale. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : None // ////////////////////////////////////////////////////////////////////////////////////////// #define TIME_INFUSION_SCALE_UNSTABLE (15) //s static void filterInfusionWeight(CONTROL_DATA_T * control_data) { int i; int infusion_sum = 0; int infusion_stable_count = 0; int infusion_max = −6000; int infusion_min = 6000; int infusion_raw_sum = 0; // add new weight reading to circular buffer and adjust index InfusionArray[ infusion_wt_counter ] = ( int ) control_data->infusion_wt_g; infusion_wt_counter++; if ( infusion_wt_counter >= SIZE_INFUSION_ARRAY ) { infusion_wt_counter = 0; } // calculate min, max and average and number of stable readings for ( i = 0;i < SIZE_INFUSION_ARRAY;i++ ) { if ( InfusionArray[ i ] < ( control_data->infusion_wt_g_filt + INFUSION_SCALE_STABLE_LIMIT ) && //only use weight if it is within stable limit InfusionArray[ i ] > (control_data->infusion_wt_g_filt − INFUSION_SCALE_STABLE_LIMIT ) ) { infusion_sum += InfusionArray[ i ]; infusion_stable_count++; } if ( InfusionArray[ i ] > infusion_max ) { infusion_max = InfusionArray[ i ]; } if ( InfusionArray[ i ] < infusion_min ) { infusion_min = InfusionArray[ i ]; } infusion_raw_sum += InfusionArray[ i ]; } //only use data if more than half data is within stable limits if ( infusion_stable_count > ( SIZE_INFUSION_ARRAY / 2 ) ) { control_data->infusion_wt_g_filt = ( float ) infusion_sum / infusion_stable_count; Infusion_scale_unstable_ctr = 0; } else { if ( ( infusion_max − infusion_min ) < INFUSION_SCALE_STABLE_LIMIT ) //if total variation over last 10 seconds is stable, use that data { // use average if spread of readings is within limits control_data->infusion_wt_g_filt = ( float ) infusion_raw_sum / ( SIZE_INFUSION_ARRAY); Infusion_scale_unstable_ctr = 0; } else { Infusion_scale_unstable_ctr++; //if scale unstable for 15 seconds, if ( Infusion_scale_unstable_ctr > DEF_PUMP_CONTROL_RATE * TIME_INFUSION_SCALE_UNSTABLE ) { ReportAlarmOrAlert( INFUSION_SCALE_UNSTABLE,_FILE_, _LINE_,0,0,0 ); Infusion_scale_unstable_ctr = 0; SetMode(MODE_PAUSE); } } } } // end func filterInfusionWeight( ) ////////////////////////////////////////////////////////////////////////////////////////// // Name : filterUrine Weight // // Description : filter urine weight using a moving average filter // and check for stable urine weight. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : None // ////////////////////////////////////////////////////////////////////////////////////////// #define TIME_URINE_SCALE_UNSTABLE (60) //s static void filterUrineWeight(CONTROL_DATA_T * control_data) { int i; int urine_sum = 0; int urine_max = −6000; int urine_min = 6000; int urine_raw_sum = 0; int urine_stable_count = 0; // add new weight reading to circular buffer and adjust index // collect urine weight measurements UrineArray[ urine_wt_counter ] = ( int ) control_data->urine_wt_g; urine_wt_counter++; if ( urine_wt_counter >= SIZE_URINE_ARRAY ) { urine_wt_counter = 0; } // compare collected measurements to allowed limits // to determine number of good and erratic readings // of weight in the array buffer // determine number of good ones for ( i = 0;i < SIZE_URINE_ARRAY;i++ ) { if ( UrineArray[ i ] < ( control_data->urine_wt_g_filt + URINE_SCALE_STABLE_LIMIT ) && //only use weight if it is within stable limit UrineArray[ i ] > ( control_data->urine_wt_g_filt − URINE_SCALE_STABLE_LIMIT ) ) { urine_sum += UrineArray[ i ]; urine_stable_count++; } // update minimum and maximum values of bag weight // for the array if ( UrineArray[ i ] > urine_max ) { urine_max = UrineArray[ i ]; } if ( UrineArray[ i ] < urine_min ) { urine_min = UrineArray[ i ]; } urine_raw_sum += UrineArray[ i ]; } // decide if the data during the buffer time was stable using // 50% good criteria if ( urine_stable_count > ( SIZE_URINE_ARRAY / 2 ) ) //only use data if more than half data is within stable limits { //only update weight if it is not being ignored if( !IgnoreUrineBagFlag ) //if data is acceptable { // average the collected data for 10 seconds // using only stable measurements control_data->urine_wt_g_filt = ( float ) urine_sum / urine_stable_count; } Urine_scale_unstable_ctr = 0; //reset unstable counter } else { // if amplitude of urine weight variation within // the array of data is acceptable if ( ( urine_max − urine_min ) < URINE_SCALE_STABLE_LIMIT ) //if total variation over last 10 seconds is stable, use that data { //only update weight if it is not being ignored if ( !IgnoreUrineBagFlag ) { // average data control_data->urine_wt_g_filt = ( float ) urine_raw_sum / ( SIZE_URINE_ARRAY ); } // reset counter of unstable measurements Urine_scale_unstable_ctr = 0; } else { Urine_scale_unstable_ctr++; // issue an alarm if scale is unstable if ( Urine_scale_unstable_ctr > DEF_PUMP_CONTROL_RATE * TIME_URINE_SCALE_UNSTABLE ) //if scale unstable for 60 seconds, { ReportAlarmOrAlert( URINE_SCALE_UNSTABLE,_FILE_, _LINE_,0,0,0 ); Urine_scale_unstable_ctr = 0; // UrineWeightStable = FALSE; // turn operational mode to KVO, stop balancing urine weight // SetMode(MODE_PAUSE); } } } } // end func filterUrineWeight( ) ////////////////////////////////////////////////////////////////////////////////////////// // Name : FilterData // // Description : Filter control data (pump speed, infusion weight, // urine weight). pump speed is filtered using a low // pass filter. Weights are filtered using a moving // average filter. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : None // ////////////////////////////////////////////////////////////////////////////////////////// void FilterData( CONTROL_DATA_T * control_data ) { // // Filter pump (motor) speed // control_data->actual_pump_speed_filt = LowPassFilter( control_data- >actual_pump_speed, control_data->actual_pump_speed_filt, PumpSpeedAlpha ); // // filter weights // if ( CurrentMode != MODE_RUN ) { control_data->infusion_wt_g_filt = control_data->infusion_wt_g; control_data->urine_wt_g_filt = control_data->urine_wt_g; Infusion_scale_unstable_ctr = 0; Urine_scale_unstable_ctr = 0; } else { // run mode // filter infusion weight filterInfusionWeight(control_data); // filter urine weight filterUrineWeight(control_data); } } // end func FilterData( ) ////////////////////////////////////////////////////////////////////////////////////////// // Name : calcBolusAmount // // Description : Calculate the bolus amount per control interval. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : bolus amount per control interval // ////////////////////////////////////////////////////////////////////////////////////////// static float calcBolusAmount(void) { float bolus_per_interval; //saline to be given as part of bolus for each interval float BolusToBeDelivered; //bolus volume left to be delivered float BolusDelivered; float time_since_last_interval; float bolus_per_interval_accurate; // in micro liters // get user bolus setting BolusToBeDelivered = getUserSetting( BOLUS_SETTING ); // get amount of bolus delivered BolusDelivered = NVRAMData.bolusDelivered; bolus_per_interval = 0.0; bolus_per_interval_accurate = 0.0; if ( (BolusToBeDelivered > 0) && (BolusDelivered < BolusToBeDelivered) ) { //bolus should be delivered over half hour, time_since_last_interval = ( float ) ElapsedTime( LastControlInterval ); getTime( &LastControlInterval ); if ( abs( ( int ) time_since_last_interval ) > 1 ) //if interval very large, or first time, do not use it time_since_last_interval = 1.0; //limit to 1 second // convert ml to micro liters and calculate amount per interval bolus_per_interval_accurate = ( BolusToBeDelivered * 1000.0 * time_since_last_interval ) / ((float)TIME_BOLUS_DELIVERY); //(total bolus * seconds per interval)/(seconds in half hour) // calculate in ml per hour bolus_per_interval = bolus_per_interval_accurate/1000.0; if ( ( BolusDelivered + bolus_per_interval ) > BolusToBeDelivered ) { //bolus delivered, stop sending any more bolus_per_interval = BolusToBeDelivered − BolusDelivered; bolus_per_interval_accurate = bolus_per_interval; NVRAMData.bolusDelivered = BolusToBeDelivered; NVRAMData.BolusTime = TIME_BOLUS_DELIVERY; } else { NVRAMData.BolusTime += time_since_last_interval; //FlowControlInterval; BolusDelivered += bolus_per_interval; //add to total NVRAMData.bolusDelivered = BolusDelivered; } }  return(bolus_per_interval_accurate); } // end func calcBolusAmount( ) ////////////////////////////////////////////////////////////////////////////////////////// // Name : calcNetGain // // Description : Calculate the net gain per control interval. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : None // ////////////////////////////////////////////////////////////////////////////////////////// static void calcNetGain(void) { float setting; float netGain_mlphr; float bolus_per_interval; //saline to be given as part of bolus for each interval netGain_mlphr = getUserSetting( NET_GAIN_SETTING ); netGain_mlphr *= 1000.0; // increase resolution to microliters setting = (float)(((double)netGain_mlphr * (double)FlowControlInterval) / 3600.0); //convert from ml/hr to ml/s //do not increase net gain target if the max infusion fluid limit is reached //this flag will be cleared if the limit is changed if ( !MaxInfusionFluidReportedFlag ) { // increment get gain by the user setting for this interval control_data.net_gain_target_accurate += setting; //if bolus has not been delivered, add that bolus_per_interval = calcBolusAmount( ); control_data.net_gain_target_accurate += bolus_per_interval; //add bolus to total } control_data.net_gain_target = (control_data.net_gain_target_accurate / 1000.0); } // end func calcNetGain( ) ////////////////////////////////////////////////////////////////////////////////////////// // Name : checkForInfusionMismatch // // Description : Check for a mismatch between the amount of infused // fluid calculated from the pump displacement and // the change in infusion weight. // // Inputs : None // // Parameters : None // // Outputs : None // // Returns : None // ////////////////////////////////////////////////////////////////////////////////////////// static void checkForInfusionMismatch(void) { float infusion_pump_displacement; float infusion_weight_delta; float infusion_error_limit; float infusion_weight_error; S32 actual_delta_range_s; // // Check Hydration (infusion) bag weight mismatch // by comparing amount displaced by pump with amount // of change in infusion weight if(ElapsedTime(LastInfusionCheckTime)>=60) //check every minute { getTime(&LastInfusionCheckTime);//set last check time to now AddInfusionWeight( control_data.infusion_wt_g_filt, control_data.accumulated_pump_displacement ); infusion_pump_displacement = GetInfusionPumpDisplacementDelta(NUM_INFUSION_DELTAS); // infusion_weight_delta = ( int ) GetInfusionWeightDelta(NUM_INFUSION_DELTAS); infusion_weight_delta = (int) GetInfusionDeltaAndTime( NUM_INFUSION_DELTAS, &actual_delta_range_s ); infusion_weight_error = abs( -infusion_weight_delta − infusion_pump_displacement ); //difference over last 15 minutes infusion_error_limit = MaxDouble( ( infusion_pump_displacement * .5 ), 25.0 ); //limit is 50% of pump displacement or 25ml, whichever is greater if (actual_delta_range_s >= NUM_INFUSION_DELTAS) { if (infusion_weight_error>infusion_error_limit ) //run_time>15 && { ReportAlarmOrAlert( INFUSION_WEIGHT_MISMATCH_ALERT,_FILE_, _LINE_,0,(S32)infusion_pump_displacement,(S32)infusion_weight_delta ); InfusionWeightStable = FALSE; } } } } // end func checkForInfusionMismatch( )

F. Air Bubble and Pressure Detection and Hydration Settings

Control subsystem 34″, FIG. 3 may also include electronic air detector 86 that prevents infusion of air into the patient. The air detector 86 is of ultrasonic type and can detect air in amounts exceeding approximately 50 micro liters traveling inside the infusion tubing 32. In one example, air detector 86 employs technology based on the difference of the speed of sound in liquid and in gaseous media. If an air bubble is detected, the pump 22′ can be stopped almost instantaneously.

The controller software reads the bubble detector output and is programmed to generate an alarm signal whenever the pump is running and bubbles are detected for more than 540 ms in an 8 minute window. The bubble detector will detect a 50 μl bubble and generate a minimum pulse of 11 ms.

On power up, the controller software may query the user to select new patient or same patient using the menus and keys discussed with reference to FIG. 13. If the same patient is selected, the controller software may restore the system settings and control values to resume operation before power was turned off.

If a new patient is selected, the software may clear the control values (such as accumulated infusion accumulated urine, bolus delivered) for the new patient. System settings are restored to their default values. The system settings that are restored from PROM to CPU memory to their default values are Bolus Amount Setting, Net Gain Settings, Maximum Hydration Settings, and Minimum Urine Setting.

Upon detection of low power condition, the software may store the system settings and other control parameters, needed to restore operation on the same patient, in non-volatile memory (PROM such as an EEPROM).

A pressure sensor may also be incorporated to measure pressure in the infusion line downstream of pump 22′, FIG. 3 and upstream the patient I.V. The software may read the pressure sensor to detect occlusions. If the pressure exceeds 15 psi for 30 seconds, for example, the controller software may report an alarm condition. If the pressure exceeds, for example, 25 psi at any time, or 10 psi for longer than one minute, the software may report an alarm condition. Meanwhile, the controller software may slow down or stop the pump for a short time to allow the occlusion to be resolved on its own before alarming the user. The software may detect when the Maximum Hydration Limit (set by the user) is reached. In run mode, the software may generate an alert if the cumulative net gain (hydration) exceeds the maximum hydration limit and stop net gain infusion but continue urine balancing. The software may allow the user to override this condition by increasing or decreasing the net gain setting at any time via the user interface.

In run mode, the software may generate an alert if the measured urine over a 30 minute period is less than the minimum urine output setting. The setting can be chosen by user, for example from 0 to 500 ml/hour. The infusion fluid weight is used to enhance accuracy of fluid delivery over time. Reduction of weight in the bag is continuously monitored in addition to the pump speed to ensure redundancy, added accuracy, and to inform the user in advance that the fluid bag is almost empty.

The urine weight output displays urine volume and urine output rate and enables automatic replacement of fluid lost in urine. The controller software measures urine weight as described herein and adjusts the pump speed to add the amount lost in urine to the Net Hydration Gain setting and Bolus Setting set by the user.

Weight measurements can be collected by software every 100 milliseconds. The following software algorithms are applied to the weight scale measurements.

The infusion weight scale reading is filtered with a 10 second moving average filter. The infusion weight scale is considered to be stable: if half of the samples are within ±16 g of the previous filtered value, or if the difference between the minimum weight reading and the maximum weight reading in the filter window is less than 16 g.

The infusion weight scale may be declared unstable if it does not meet the stable criteria (defined above) for 15 seconds. The urine weight scale reading is filtered with a 60 second moving average filter. The urine weight scale is considered to be stable if half the samples are within ±100 g of the previous filtered value, or if the difference between the minimum weight reading and the maximum weight reading in the filter window is less than 100 g.

The urine weight scale may be declared unstable if it does not meet the stable criteria (defined above) for 60 seconds. If the weight scale is not stable, the system switches to the PAUSE (KVO) and alerts the user.

If a weight scale (hydration or urine) is not stable, the system switches to the PAUSE (KVO) and alerts the user. KVO means that no urine volume is replaced, hydration flow is reduced to value sufficient to prevent vein from closing (KVO-Keep Vein Open) and to maintain baseline or minimum hydration. The user has an option to CLEAR or cancel the condition and the infusion amount equal to the amount of urine accumulated during PAUSE will be infused into the patient by software algorithm. The later will only occur if the weights scales are now reliable and stable. In FIG. 9B, the abnormal hydration fluid measurement is indicative of a replacement of the source of hydration fluid and the corrective action taken by the controller software is the generation of an alarm signal.

The following additional functions may be embodied by the software using data from the weight scales.

During the run mode, the software compares the amount of volume delivered as determined by the pump rate against the amount of volume delivered as determined by the weight change of the hydration fluid bag scale. If this difference over a 15 minute period is greater than 50% or 25 ml, then the software generates an alarm. During infusion, if the 2 liter urine bag measures, for example, more than 1.8 kg, the software shall generate an alert. During infusion, if the software measures the standard one liter hydration bag weight to be less than 50 g (almost empty) or if the software measures the difference between the initial hydration bag weight and the current bag weight to be greater than 950 g, it can generate an alarm.

In run mode, the software can generate an alert and go to pause mode if the measured urine drops more than 50 g over a 5 minute period. There should not be sudden drops of urine weight. This may indicate opened valve or disconnected or opened tube.

In run mode, the software may generate an alert and go to pause mode if the measure urine increases more than 500 g over a 5 minute period. This is an unlikely “physiologic” event and is identified as hardware failure or user misuse such as inadvertently placing additional tension or weight on the hook.

The urine bag may also include a label instructing the nurse to push pause on controller console 82, FIG. 3 before emptying the urine bag. The function of the pause button is explained further below.

One Prototype System

One prototype system includes console 500, FIG. 18 and infusion and urine collection sets. Motion restraining clamp 502 is for urine bag 504 chain 506. The integrated infusion set includes an IV bag spike, a Luer-to-Foley connector for priming, and a urine collection set includes an integrated urine bag. The power requirements are 115/220 VAC, 60/50 Hz, 25 VA. An auxiliary ground post (potential equalization) for the device is on the rear of the case (not shown). An RS 232 port is also provided. When mounted on an I.V. Pole, the system requires an area of approximately 20×20 inches. Console 500 is placed on the pole so that the urine collection bag 504 is above floor level and not touching the floor or other equipment. Urine collection bag chain 506 is passed through motion restrictor ring 502 to prevent excessive swinging of the bag. Urine collection bag 504 is below the level of patient to facilitate urine drainage, and urine 504 and hydration fluid 512 bags are hanging freely on hooks 514 and 516, respectively, and not supported or impeded. Protection tubes 517 and 519 shown in phantom may be provided about hooks 514 and 516. The urine 518 and hydration 520 tubing should not kinked or pinched, and should not pull or strain the weight measuring devices.

The system maintains hydration balance by measuring patient urine output and infusing hydration fluid (prescribed by physician) into the patient I.V. to balance the fluid lost in urine. In addition to urine volume replacement, the system implements a user-set net fluid gain. Net fluid gain is defined as the amount of fluid in ml/hour infused into I.V. in addition to the replaced volume of urine. The system also allows rapid infusion of a Bolus of fluid at the user request. The amount of Bolus can be selected by user and typically the bolus is infused over 30 minutes. Bolus is infused in addition to the Net Fluid Gain and the replaced volume of urine. Console 500 includes a microcontroller device that has means for measuring urine and the ability to infuse hydration fluid into the patient. The infusion set allows the console to pump fluid from a hydration fluid bag to the patient at a controlled rate. The disposable urine collection set collects the patient's urine to allow it to be measured accurately. Console 500 is also equipped with an internal battery that can sustain operation in the event of power outage or during short periods of time, for example, when the patient is moved. Console 500 includes roller pump 530, user interface 532, two weighing scales (not shown), air detector 535, post-pump pressure sensor 534, an electrical connector for AC power, and mechanical interfaces for holding the set in place. Console 500 controls the rate at which fluid is infused and monitors urine volume by weight measurement.

To initiate treatment, the system requires: a) peripheral I.V. access 536, b) a urinary Foley catheter 538 and c) an appropriate number of one liter bags with the physician prescribed hydration fluid. The set is automatically primed by console 500. During the operation, the user is responsible for a) draining the urine bag when full, b) replacing hydration fluid bags when empty, and c) responding to alarms and alerts issued by the system. Interface 532 can display four lines of text at a time. The system automatically scrolls through the system parameter display items. Each item is displayed for 5 seconds. The user can scroll to the next system parameter display item by pressing scroll key 600, FIG. 17. Depending on the system condition and operating mode, the following parameters are displayed: the net fluid gain accumulated since the start of the therapy in ml, the total fluid infused since the start of the therapy in ml, the total urine collected since the start of the therapy in ml, the urine rate averaged over the last 15 minutes in ml/hour, if bolus delivery is in progress, the system displays amount of time remaining to complete bolus delivery, the operating mode (Run, Pause or Stopped), and the total therapy time. The software also displays the source of power (DC or battery), the amount of estimated battery life in minutes and the state of battery charge in percent. Alert or alarm messages, if such a condition exists, are also displayed. The system allows the user to enter following parameters: desired Net Fluid Gain in ml/hour, Bolus Amount in ml, maximum allowed accumulated Net Fluid Gain in ml, and minimum urine output in ml/hour for alert only.

The system also includes the following features designed to protect the patient from potentially hazardous conditions and malfunctions and alarm the user as needed. An air detector 535 with automatic infusion pump 530 shut-off, post-pump downstream pressure sensor 534 to detect occlusions, and pump motor speed monitoring by an optical encoder, weight scale monitoring of infusion fluid to detect leaks and pre-pump upstream occlusions, weight scale monitoring of urine volume to detect leaks and urine collection set occlusions, free flow protection device 540 (pressure valve), and a pump door open detector with automatic motor shut off, critical components of these safety circuits are tested automatically prior to each therapy. Some components are monitored for integrity continuously during therapy.

To initiate treatment, medical grade power cord 510 is connected to the power plug receptacle on the rear of the device. The device is then plugged into a grounded electrical outlet. The “POWER ON/OFF” key 602, FIG. 19 on the front panel is then pressed. A short tone indicates the diagnostic self-test is starting. The message “Power on Self Test In Progress” is displayed. The device progresses through the test for approximately 30 seconds. Confirm that the AC MAINS symbol 604 located on the front panel is illuminated. If the self-test terminates with an audible alarm and an error message on the display, make a note of the error code displayed. If error cannot be corrected, press the POWER ON/OFF key, wait 5 seconds, and then repress the “POWER ON/OFF” key as above. The System progresses to the Same Disposable Set, New Disposable Set. The following message is displayed “Press ACCEPT 606 for Same Patient or CLEAR 608 for New”. Pressing the ACCEPT KEY restores all the parameters used for therapy before power was turned off including Therapy settings including Bolus administration and Net Gain target, and Therapy parameters such as elapsed time, urine made and fluid infused. Pressing CLEAR KEY 608 indicates that the new infusion set is used on the same patient or that a new patient therapy is started. All settings and parameters are restored to zero or system defaults. Before therapy is started the System shall be PRIMED. Priming procedure requires loading and setting of disposables. Proceed as follows to load the INFUSION SET tubing onto the console. Visually examine the package to determine that the package has not been opened or damaged during shipping. Open the package. Release the ties holding the set to the packing card. Carefully remove the INFUSION SET from the packaging. Use the I.V. pole to hang the set while preparing to load. Preserve sterility. Air detector 535 is connected downstream of the pressure sensor. Start by connecting the infusion line air hydrophobic filter 542 to pressure transducer connector 534 on the front of the console. Use a gentle but firm turning motion until it stops. Open the pump door 531 and load the pump segment tubing over the rollers. Assure that the clips on ends of the raceway are lined up with the tube segment. Close the pump door firmly until a click is heard. Check that the tubing is aligned correctly. When the pump door is open the pump is stopped and can not move. Spike a hydration bag 512 with the IV Set spike using standard technique. Ensure that the drip chamber 550 is at least 50% full by gently squeezing and releasing the chamber. Hang the full 1 liter hydration fluid bag on the left chain hook 552 of the console. Ensure free swinging motion of the bag. The system is designed for use with 1 (one) LITER infusion bags only. Do not use any other bag sizes. Load the infusion set tubing segment immediately to the right of the pressure sensor into air detector 535. Assure that the tubing is firmly seated at the bottom of the air detector channel. Use stretching or flossing motion to set the tube in the slot. Handle 537 may be provided to seat the tubing in sensor 535. The system is equipped with the sensitive (50 micro liter) ultrasonic air detector. If tubing is not loaded into the detector properly, the System will not operate. Hang the empty urine collection bag 504 on the right chain hook 554 of the console. Ensure free swinging motion of the bag. Ensure that the chain 506 of the urine bag is passed through retainer clamp 502. The retainer clamp will prevent excessive swinging of the urine bag. Ensure that the bag is hanging unobstructed and unsupported to assure proper weight measurements. Check to see that the drain valve 560 at the bottom of the urine collection bag 504 is fully closed. If not, you should close the valve. Connect a luer connector (normally used for I.V.) on patient end of the infusion set to the foley catheter adapter on the patient end of the urine collection set tubing. Use the Foley-to-luer adaptor to make the connection. This adapter is intended for priming only and is discarded before patient use. Use the I.V. pole to support the length of tubing. Ensure that tension is not exerted on the bags and the bag suspension system. Make sure the clamps on the withdrawal and infusion tubing are open. Press the PRIME button 610 and Press the ACCEPT key 606 to start priming the INFUSION SET. The pump will run and stop independently for approximately 3 minutes. Approximately 150 ml of fluid will be pumped from the hydration bag 512 into the urine collection bag 504. While the pump is running, the user may tap gently on the tubing and/or squeeze the drip chamber to release any bubbles. The user should also inspect the infusion set for any leaks during priming. The user can discontinue priming by pressing the stop key 612. When the pumps stop, the user may carefully examine the entire infusion set and the filter to assure it fully primed and that no air is present in the blood tubing. If no air is present, the user may proceed to initiating therapy. If any alarm occurs during priming, refer to the Alarm Section of this manual for more detailed help in correction of these alarms. Once the problem has been corrected, the user should re-prime the infusion set prior to initiating therapy. At the end of automatic priming the System will display message: “Check Weight Bags. Don't Touch Bags.” It is important not to interfere with the bag suspension system at this time. Disconnect the INFUSION SET I.V. connector from Foley Connector of the Urine Collection Set. Remove and discard the Luer-To-Foley adapter. The user may close the pinch clamp on the infusion line to prevent fluid leakage. Connect the infusion set connector to the already inserted I.V. access device. Assure that no air enters the system. Turn the connector until it clicks closed. Close the pinch clamp the urine collection tubing prevent fluid leakage. Connect the urine tubing connector from the urine collection bag to the Foley catheter. Assure the connection does not leak. Press the run button 612 to start therapy. The system has three user settable parameters: Net Gain Setting, Maximum Hydration Setting, and Minimum Urine Output Setting. All of these parameters can be viewed and changed using the MENU Key 614. Parameters are changed by selecting from the scrolled list using UP and DOWN Arrow keys 616 and 618. To change the parameter to selection the user needs to press the ACCEPT Key 606. If the user does not press the accept key shortly after making the selection, the screen is cleared, the new value is rejected and the system continues with the current value. New parameters are implemented only after the ACCEPT key is pressed. This value is the amount of hydration (in ml/hour) that the patient will receive IN ADDITION to the replacement of urine volume. The net gain is selectable from 0 to 500 ml/hr in increments of 25 ml. This setting can be changed at any time during therapy using the MENU key selection 614 and the UP and DOWN Arrow keys. The FLUID BOLUS is given to the patient is in addition to NET GAIN amount. Default NET GAIN is set to ZERO when the New Patient Therapy is selected. This value is the maximum total amount of NET GAIN hydration (in ml/hour) that the patient will receive IN ADDITION to the replacement of urine volume. The value for maximum hydration is selectable from 0 to 1,500 ml in increments of 100 ml. This setting can be changed at any time during therapy using the MENU key selection and UP and DOWN Arrow keys. After this value is reached, only urine volume replacement will occur (net zero replacement). The user is notified by an alert that this level is reached. This number sets the minimum desired urine output level. This setting does not affect the System performance. If the urine output is consistently below the set value user is notified by an alert sound and a display message “Minimum Urine Level Not Reached”. The minimum urine output setting shall be selectable from 0 to 150 ml/hr in increments of 50 ml/hr using UP and DOWN Arrow keys. The System is designed to stop automatically and alarm when the Hydration fluid bag is almost empty (or with approximately 50 ml of fluid remaining in the bag). Hydration fluid bags can be also changed at any time by pushing the STOP button and stopping the pump. If user desires to replace bag that is not empty, user shall push STOP button to avoid air in the circuit. If the bag reaches the minimum acceptable volume, the System will be stopped. The message “Saline Bag Empty. Replace Saline Bag” will be displayed and alarm sound. The alarm can be silenced using SILENCE button for 2 min. To continue the operation press CLEAR button. The bag is replace using standard technique common to all I.V. sets with high flow drip chambers. After the bag is replaced, therapy can be restarted by pushing the RUN button. System will automatically account for the change of weight. The system will automatically replace fluid lost by patient in urine while the pump was stopped. This may result in temporary high infusion rate. If the urine bag is full, the system will automatically switch to PAUSE mode. In the PAUSE mode, the system will issue an alert and stop urine volume replacement. To maintain patency of the venous access, hydration will continue but only at a pump flow of 70 ml/hour. The user can empty the bag when full or at any time if desired by the user. The urine collection bag may emptied by performing the following steps. The system is designed to alarm the user when the urine collection bag is almost full. Urine bag holds 2 liters of urine. The system will display message: “Urine Bag Full, Empty Urine Bag”. Push the PAUSE KEY to switch to Pause Mode. Note the total volume in the urine collection bag. Record it appropriately.

It is the responsibility of the user to push PAUSE button before draining the urine bag. Failure to do so, draining bag during without Pausing the System Operation may result in incorrect measurement and display of urine volume and alarms. Open the drain valve at the bottom of the URINE COLLECTION BAG COUNTERCLOCKWISE and drain into a container. It is recommended that the user drain the urine into a marked container and record that value prior to discarding the urine. When in PAUSE mode, the system will not replace fluid lost in urine. It is user responsibility to push the PAUSE or RUN button to restart automatic urine volume replacement. Therapy will not restart automatically until PAUSE or RUN button is pushed. Close the urine bag valve. PUSH PAUSE KEY to switch back to RUN mode. Do not leave system in the Pause mode unless intended. The user may empty the urine collection bag prior to it being full. Thus, the total number of times the bag was emptied may overestimate the total fluid removed. The BOLUS Button allows the user to infuse additional fluid into I.V. when clinically indicated. The volume set for the BOLUS is always delivered over 30 minutes. BOLUS Key can be only used when the device is running. If the device is PAUSED or STOPPED, a bolus cannot be initiated. Push BOLUS key. The system will display the BOLUS AMOUNT SELECTION Menu. Select bolus amount from 0-250 ml in increments of 50 ml using Navigation Keys. Push ACCEPT Key to confirm the selection. The bolus amount will be delivered over 30 minutes in addition to the user set Net Gain and Machine Set Urine Volume Replacement. During the BOLUS delivery the System will display the “Bolus Remaining” volume and bolus “Time Remaining” information automatically. Bolus Volume is infused in addition to the user set NET GAIN and the replaced URINE VOLUME. If the BOLUS is interrupted by user PAUSE or the System being STOPPED by the user, BOLUS delivery will be completed as soon as the system returns to normal operation. The Advance and Pause Keys help user perform maneuvers frequently encountered in I.V. Hydration therapy. The pause mode is similar to the KVO (Keep Vein Open) mode frequently used in I.V. therapy. It is intended to disable urine volume monitoring and replacement when the urine bag is drained or when the patient is moved or urine drainage is re-arranged. Press and HOLD the ADVANCE KEY to displace fluid and air though the INFUSION SET. Releasing the ADVANCE KEY will stop the pump in 2 seconds. If the ADVANCE KEY is held continuously for longer than 30 seconds the pump will automatically stop. Releasing and pressing and holding the key again will allow pump to run for additional 30 seconds.

Air detection is disabled during ADVANCE KEY operation. It is the user's responsibility to prevent the infusion of air into the patient. The software stops the urine volume replacement control when the user presses the pause key and the system is in run mode. The user may drain the urine bag during this mode. The software shall resume operation when the user presses the PAUSE key and the system is in pause mode. The system runs the pump at a rate of 70 ml/hr to keep the vein open and maintain I.V. hydration. During pause mode, the system generates a low volume beeping. After 15 minutes, the System will increase the volume to high to bring to user's attention that the patient is not receiving urine volume replacement. Upon exit from Pause mode and into run mode, the System adapts to the infusion and urine bag weight changes to correctly resume hydration control. When the FMS System is PAUSED, the Urine volume is not being replaced. Infusion is set to 70 ml/hour, until the user terminates the PAUSE. Silencing and Clearing an Alarm may not eliminate the Alarm cause. Carefully investigate and correct all Alarms and Alerts.

The alarms generated by the FMS System indicate the presence and severity of the alarm. The lighted LED and type of sound represent the general level of importance of the current operating conditions to the user. Press the SILENCE key to silence the alarm for 2 minutes while performing corrective actions. Respond to the information displayed on the screen and correct the conditions that caused the ALARM.

Press the CLEAR Key to reset the alarm. If the FMS-1 is still in RUN Mode and the alarm condition is still present, the ALARM will re-annunciate. If the FMS-1 is in STOP Mode, the Alarm condition may be cleared but may re-annunciate if the condition has not been removed when the system is restarted. Some Alarms such as System Malfunction Alarms can not be cleared or silenced unless Power is turned OFF and ON. Depending on the cause of an Alarm or Alert System may respond in two ways: alarm the user and stop the pump (for example if Air is detected or hydration fluid bag is empty) and alarm the user and stop urine volume replacement while maintaining pump flow at 70 ml/hour (as for example if urine bag is full).

While the system will provide information on the most likely causes of the alarm, the user must exercise caution and examine all possible options if the information displayed does not solve the problem.

The user can select the maximum net gain for single patient THERAPY from 0 to 1,500 ml. When this maximum net gain is reached, the system generates an alert. Without user intervention further net gain is not added to the urine volume replacement, patient therapy is “net zero” balance. The user can override this condition by increasing the net gain setting at any time. Clear the alarm if no further Net Gain is desired or change the Maximum Net Gain Setting.

The minimum urine not reached alert is designed to inform the user that over the period of 30 minutes patient's urine output was below user selected minimum level. This Alert does not affect the System operation and intended to provide information to enable the user to make clinical decisions. User can choose to Clear the Alarm, Change the setting or Silence this alarm. The air detected alarm significant amount of air is detected by the ultrasonic air detection. The infusion pump is stopped immediately until user corrective action. This alarm can be caused by air entrained from the damaged or disconnected tubing, air entrained from the drip chamber, or a tube dislodged from the air detector slot. Recommended action includes a check of Leaks and Drip Chamber level, Use of the advance Mode to remove/aspirate air bubble, or a restart of therapy by pressing RUN key after removing the air.

If an Infusion Set Occlusion Alert is generated, the pressure sensor has detected a downstream occlusion of the infusion Line. The Infusion pump is stopped immediately until user corrective action. This alarm can be caused by closed clamp, a kinked tube, or an occluded I.V. Recommended Action includes a check of the clamps, a check of the tubing, or flushing the I.V. following the accepted clinical technique.

The Urine Bag Full Alert indicates the system has detected that the Urine Bag is full using the weight scale. Hydration continues at NET GAIN RATE or 70 ml/hr, which ever is higher. Urine volume replacement is disabled during this time. After the urine is drained, therapy will be restarted as before the alert. Recommended Actions include checking the urine bag level, pressing the PAUSE key, draining the urine bag using accepted clinical technique, and push PAUSE key again.

The Fluid Bag Empty Alert indicates the system has detected that the Hydration Fluid Bag is almost empty. There can be approximately 50 ml of fluid left in the bag. System automatically STOPS the hydration pump. Recommended Actions include checking fluid bag level, replacing the bag using accepted clinical technique, and pushing the RUN key.

If there is a less than 10 minutes battery life remaining and the system is powered from battery, the System generates an alert with a low volume and displays message “Battery Low”. If there is a less than 2 minutes battery life remaining and the system is powered from battery, the software generates an alarm with a high volume and display message “Battery Critically Low, Connect AC now”.

The system monitors urine weight for abrupt increase that can not be explained by normal urine output. If an abrupt increase of urine weight is detected an Excessive Urine Weight Increase Alert message is issued to the user. The system is automatically switched to PAUSE mode. Hydration continues at 70 ml/hr. Urine volume replacement is disabled during this time. User can CLEAR the alert and therapy will be restarted as before the alert. This alarm can be caused by an object pulling on the urine scale hook, additional weight added to urine bag, or a hardware malfunction. Recommended Actions include ensuring that Urine collection bag is freely hanging on the right side hook, clearing the Alert, and push PAUSE key after correcting the condition.

The system monitors urine bag for sudden decrease of weight. If such decrease occurs during therapy a Urine Bag Leak Alert is issued. This alarm can be caused by the user draining urine without pushing the PAUSE Key, and/or a leak from the bag. Recommended Action includes checking for leaks and checking the tubing.

The system relies on weight scales to determine urine output and fluid replacement rate. If the device is excessively bumped the weight scale readings can become erratic and unreliable. The System automatically detects such conditions and issues an Unstable Scales Alert. If the weight scale is not stable, the system enters the PAUSE mode automatically. Whenever System is in the PAUSE Mode, urine volume is not being replaced. The patient receives 70 ml/hour. When in the PAUSE mode, the System will beep at a low rate and volume. After 15 minutes, the System will increase the volume to high to bring to user's attention that the patient is receiving only the KVO rate of hydration. Recommended Action includes bringing the system to rest and push PAUSE key to restart balancing. During patient hydration System monitors the weight of the hydration fluid bag and compares it to the pump flow rate. If serious mismatch is detected an Infusion Weight Mismatch Alert is issued and the Pump is stopped. This alarm can be caused by a disconnected tube, a kinked tube or other kind of Pre-Pump occlusion, or a leaky bag or tube. Recommended Action includes checking for leaks, checking for occlusion, and a restart therapy if the condition is corrected by pushing RUN key.

If the Pump Door is opened while pump is running, the system generates low volume beep and displays a Pump Door Open Alert message. If the pump door is opened when the system pump is not running, a message indicating that pump door is open will be displayed. Whenever the pump door is opened, the pump rollers will not move and pump will not RUN.

A Prime Test Failure alert may occur at the end of priming. The system checks a) the performance of the weight scales by comparing them to each other, b) the pressure Sensor, and c) the air detector. If this test does not pass, patient therapy will not be allowed. Following message is displayed “Prime Test Failed” followed by the failed component (i.e. weight scale, pressure sensor or air detector). This alarm can be caused by hardware failure, the user interfering with weight scale measurement, incorrect connection of fluid path during priming, bags not on hooks, a tube not in air detector, or a disconnected pressure sensor tube. Recommended actions include ensuring that the infusion set is connected to the Urine Collection bag and fluid is pumped from former to later, ensuring that urine collection bag is freely hanging on the right side hook and the hydration fluid bag is freely hanging on the left side hook, ensure the proper connection of pressure and air sensors, and repeating the procedure using the PRIME key.

System malfunctions result from internal system diagnostic tests continuously executed by the system when in operation. They typically indicate a possibility of a component malfunction. An alarm is issued and the system is stopped. System malfunctions, in most cases can not be cleared. User is advised to turn power off and on once. If the system malfunction condition remains, the system should not be used.

Although specific features of the invention are shown in some drawings and not in others, this is for convenience only as each feature may be combined with any or all of the other features in accordance with the invention. For example, there are other ways to determine a patient's urine output and other ways to quantify the amount of hydration fluid administered to the patient. There are also other ways to redundantly check the amount of hydration fluid administered the patient. Also, the words “including”, “comprising”, “having”, and “with” as used herein are to be interpreted broadly and comprehensively and are not limited to any physical interconnection. Moreover, any embodiments disclosed in the subject application are not to be taken as the only possible embodiments. Other embodiments will occur to those skilled in the art and are within the following claims.

In addition, any amendment presented during the prosecution of the patent application for this patent is not a disclaimer of any claim element presented in the application as filed: those skilled in the art cannot reasonably be expected to draft a claim that would literally encompass all possible equivalents, many equivalents will be unforeseeable at the time of the amendment and are beyond a fair interpretation of what is to be surrendered (if anything), the rationale underlying the amendment may bear no more than a tangential relation to many equivalents, and/or there are many other reasons the applicant can not be expected to describe certain insubstantial substitutes for any claim element amended. 

1. A method of addressing contrast induced nephropathy, the method comprising: injecting a contrast agent into a patient; imaging the patient; and inducing diuresis to drive any contrast agent through the patient's kidneys to reduce its toxic effects on the kidneys and prevent damage to the kidneys by: setting a desired fluid balance, collecting urine expelled by the patient in a urine collection bag, weighing the urine collection bag, employing a pump to infuse the patient with fluid from a fluid source, weighing the fluid source, automatically adjusting the pump based on the weight of the urine collection bag and the weight of the fluid source and controlling the amount of fluid infused into the patient based on the amount of urine expelled by the patient and the set desired fluid balance, determining if a bolus amount of fluid is required for the patient in addition to the fluid infused to achieve the desired fluid balance and if so setting a desired bolus amount, and if a bolus amount was set, automatically controlling the pump to infuse the set bolus amount into the patient.
 2. The method of claim 1 further including the step of administering a diuretic to the patient.
 3. The method of claim 1 in which collecting urine expelled by the patient includes catheterizing the patient.
 4. The method of claim 1 in which catheterizing the patient includes inserting a urinary catheter in the urinary tract of the patient.
 5. The method of claim 1 in which weighing the urine collection bag includes providing an indication when a urine collection bag has reached its capacity.
 6. The method of claim 1 in which weighing the fluid source includes providing an indication when the fluid source is low on fluid. 